Spell
EquipExecution of the Contract
View:
3544
You can reveal 1 Ritual Monster in your hand; the equipped monster becomes the revealed monster's Level, until the end of this turn (even if this card leaves the field). If this card is sent to the GY because the equipped monster is Tributed: You can target 1 monster your opponent controls; destroy it. You can only use each effect of "Execution of the Contract" once per turn.
Execution of the Contract — Power Evaluation
Final Score: 52 ± 6 · Confidence: Medium
- Intrinsic: 49 · Deck: 53 · Meta: provisional
- Primary role: Utility · Secondary: Removal
Why it scores here
The card's main job is to set the Level of the equipped monster to a Ritual monster revealed from hand, which is a supporting role for Ritual Summons rather than a standalone engine. Its only interaction is a conditional destroy that needs the equipped monster to be Tributed, so it does not reliably produce board advantage. Its strength is that it is a single-copy slot that appears in 12 of 12 sampled decks across several archetypes, which confirms it is practical, but that inclusion is not evidence of raw power. High stats played no role, and no combo data exists to show what it converts into in practice.
Axis scores
| Axis | Score | Evidence |
|---|---|---|
| Accessibility | 55 | The sample shows it in 12 of 12 decks at one copy each, but its activation needs a Ritual monster in hand, so access is conditional (observed, inferred). |
| Combo & Conversion | 40 | The text converts the equipped monster's Level but no combo boards are recorded, so conversion is text-only inference (inferred). |
| Resource Economy | 35 | No card advantage or refuel is described; the only value is a conditional destroy when the equipped monster is Tributed (verified). |
| Effect & Interaction | 45 | Targets and destroys one opponent monster, but only after the equipped monster is Tributed, which limits how often it applies (verified). |
| Material Utility | 10 | It is an Equip Spell and cannot serve as material; it provides no Level or attribute body of its own (verified). |
| Resilience & Flexibility | 40 | The Level change lasts even if the card leaves the field, but the card itself is a fragile Spell on the field and its destroy only works from the GY (verified, inferred). |
| Deck-Building Efficiency | 80 | One copy per deck, no garnet or lock text, and the 12-deck sample shows it fits across archetypes at a single slot (observed). |
Calculation
Weight profile: 0.7 Utility + 0.3 Removal. Intrinsic ≈ 49, Deck ≈ 53, Meta = provisional. Modifiers: none. Final formula: 0.40*Intrinsic + 0.60*Deck
Strengths
- Runs as a single copy in all 12 sampled decks across 7 archetypes, so it is consistently playable
- Level-setting makes a Ritual monster from hand usable as a Ritual Summon enabler
- A GY trigger can destroy an opponent monster when the equipped monster is Tributed
Weaknesses
- Needs a Ritual monster in hand to activate, so it is dead without one
- The destroy requires the equipped monster to be Tributed, which is narrow
- No combo data shows what it converts into in practice
Counters / choke points
- Standard Spell removal or destruction on the equipped monster
- Opponent monster removal before the Tribute happens
Best use
Ritual Level-setter and conditional removal in Ritual-based decks. Decks: Megalith, Libromancer, Impcantation. Suggested copies: 1.
Evidence & gaps
- Verified: Card text: reveal 1 Ritual monster in hand to set the equipped monster's Level until end of turn; Card text: GY trigger to destroy 1 opponent monster only if the equipped monster was Tributed; Once per turn per effect; Single copy in all 12 sampled decks
- Observed: Appears in 12 of 12 sampled decks across 7 archetypes; Strongest co-occurrence with Megalith partners at 58.3%
- Inferred: Functions as a Ritual Summon enabler rather than a standalone engine; Conditional access depends on holding a Ritual monster
- Data gaps: no combos supplied, so combo conversion is text-only inference no guides supplied no banlist token; assumed 3 copies (unlimited) no usage statistics (StatisticsCard), so inclusion is inferred from the deck sample only